-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Doc] better documention #747
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool! FYI i think it's better to include native speakers as reviewer.. Again, better to break this down into multiple PRs, otherwise it's hard to do exhaustive reviews
Any native speaker in @taichi-dev? Maybe we can ask @yuanming-hu for help? |
Let me take a pass first. |
One more high-level thing: should we use in-place documentation? @archibate @k-ye This will allow us to write documentation together with code. I think we can have two parts: tutorials and a more complete API reference. Tutorials are written by human and API reference generated automatically. |
Sounds like a |
Right, we use
I agree - that's why I believe we should have both tutorials and API references. |
Fine, ;et's keep some critical parts to be human-written, like the definition of tensor&vectors. And non-critical parts like the API of GUI, we can machine gen it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for updating the documentation. This is really helpful. I'll take a pass now to fix minor writing issues.
Before I do my pass, do you mind doing me a favor and fix these Sphinx warnings? No rush on this. Thanks!
|
No problem! Fixed all WARNINGs except for contributor_guideline.rst, how to fix that? Seems related to the link. |
Thanks! I'm taking a pass. Adding a space after |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good in general! I took a pass through atomic, contribution guide, and syntax. I also left a few minor places for you to fix. I'll take a pass through vector and scalar_tensor tomorrow.
A few tips to improve your writing:
- Proofread before posting anything. I usually read carefully what I typed 3-5 times before I click post or submit
- Pay attention to details, such as
a
,the
, punctuation and low-level formats - Be calm, be positive, and be professional
- Use a spellchecker (I use Grammarly)
Travis can't download openssl? Excuse me? |
Finalized the remaining two files. Thanks for contributing to the documentation! It's hard to make perfect, but hopefully, readers will catch and fix our errors later. |
Related issue = #736
[Click here for the format server]